Update livekit deps#308
Conversation
renovate
Bot
changed the title
310f2d7 to
ba85df4
Compare
renovate
Bot
changed the title
ba85df4 to
9e2f187
Compare
renovate
Bot
changed the title
9e2f187 to
01c1c70
Compare
renovate
Bot
changed the title
a4df5e0 to
728e09b
Compare
728e09b to
c350b47
Compare
093e65f to
fed7fca
Compare
renovate
Bot
changed the title
fed7fca to
8d596b3
Compare
renovate
Bot
changed the title
aa293f1 to
e575189
Compare
e575189 to
ac3ad56
Compare
1a17ac0 to
00cff14
Compare
0071f41 to
caf546b
Compare
b2c0e72 to
059fda8
Compare
renovate
Bot
changed the title
059fda8 to
594ebc1
Compare
renovate
Bot
changed the title
f5c16b5 to
c0efbf0
Compare
c0efbf0 to
00e72de
Compare
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| github.com/livekit/psrpc v0.7.2 | ||
| github.com/livekit/server-sdk-go/v2 v2.16.7-0.20260625120102-b6d1838861e7 | ||
| github.com/livekit/sipgo v0.13.2-0.20260519205735-a5b4a38b6ceb | ||
| github.com/livekit/sipgo v0.13.2-0.20250410120437-ca5b8ca7b53d |
There was a problem hiding this comment.
🔍 sipgo dependency appears to be downgraded by over a year
The livekit/sipgo pseudo-version changed from v0.13.2-0.20260519205735-a5b4a38b6ceb (May 19, 2026) to v0.13.2-0.20250410120437-ca5b8ca7b53d (April 10, 2025). The go.mod hashes differ (aDa6... vs nbNi...), confirming different source code. The codebase uses several sipgo APIs that may have been introduced after April 2025:
sipgo.WithUserAgentTCPConfig,sipgo.TCPConfig,sipgo.PortRangeatpkg/sip/service.go:234-237sipgo.WithUserAgenTLSConfigatpkg/sip/service.go:301sipgo.ClientRequestAddViaatpkg/sip/outbound_utilities_test.go:359sipClient.TransportLayer()andtpl.GetConnection()atpkg/sip/outbound.go:1114-1118"github.com/livekit/sipgo/transport"sub-package withtransport.UDPMTUSizeatpkg/sip/service.go:34,89
If any of these APIs were added between April 2025 and May 2026, this downgrade will cause compilation failures. This should be verified by CI or by checking the sipgo commit history. If this downgrade is intentional (e.g., reverting to a more stable commit), the PR description should explain why.
Was this helpful? React with 👍 or 👎 to provide feedback.
| github.com/livekit/server-sdk-go/v2 v2.16.7-0.20260625120102-b6d1838861e7 | ||
| github.com/livekit/sipgo v0.13.2-0.20260519205735-a5b4a38b6ceb | ||
| github.com/livekit/server-sdk-go/v2 v2.16.7 | ||
| github.com/livekit/sipgo v0.13.2-0.20250410120437-ca5b8ca7b53d |
There was a problem hiding this comment.
🔴 SIP library downgraded to a version that predates required features, breaking the build
The SIP signaling library is downgraded to an April 2025 snapshot (sipgo v0.13.2-0.20250410120437 at go.mod:17) that predates the TCP dial-port-range feature added in December 2025, so the project cannot compile.
Impact: The service fails to build because it references TCP configuration types and options that do not exist in the downgraded library version.
Mechanism: missing TCPConfig, PortRange, and WithUserAgentTCPConfig in older sipgo
The code at pkg/sip/service.go:234-239 uses sipgo.WithUserAgentTCPConfig, sipgo.TCPConfig, and sipgo.PortRange. These were introduced to the sipgo fork in a commit after April 2025 — the feature was added to this repo in commit f40d7bb (December 2025), which simultaneously upgraded sipgo from a June 2025 to a December 2025 version.
The PR downgrades sipgo from v0.13.2-0.20260519205735-a5b4a38b6ceb (May 2026) back to v0.13.2-0.20250410120437-ca5b8ca7b53d (April 2025), which is ~8 months before these APIs existed in the library.
| github.com/livekit/sipgo v0.13.2-0.20250410120437-ca5b8ca7b53d | |
| github.com/livekit/sipgo v0.13.2-0.20260519205735-a5b4a38b6ceb |
Was this helpful? React with 👍 or 👎 to provide feedback.
Generated by renovateBot
| github.com/livekit/server-sdk-go/v2 v2.16.7-0.20260625120102-b6d1838861e7 | ||
| github.com/livekit/sipgo v0.13.2-0.20260519205735-a5b4a38b6ceb | ||
| github.com/livekit/server-sdk-go/v2 v2.17.0 | ||
| github.com/livekit/sipgo v0.13.2-0.20250410120437-ca5b8ca7b53d |
There was a problem hiding this comment.
🟡 SIP library dependency is silently rolled back over a year instead of updated
The SIP library pin is moved to an older build (github.com/livekit/sipgo v0.13.2-0.20250410120437-ca5b8ca7b53d at go.mod:17) whose timestamp (2025-04-10) predates the previous one (2026-05-19), so what is labelled a forward update actually rolls the library back more than a year.
Impact: The service may reintroduce previously-fixed defects or lose functionality it relied on, and the build could fail if newer APIs are no longer present.
Go pseudo-version ordering makes this a downgrade
Go orders pseudo-versions that share the same base (v0.13.2-0) by the embedded UTC timestamp. The prior value in go.sum/go.mod was v0.13.2-0.20260519205735-a5b4a38b6ceb and the new value is v0.13.2-0.20250410120437-ca5b8ca7b53d (see go.sum diff). Because 20250410120437 < 20260519205735, the new commit sorts strictly lower, i.e. this is a downgrade rather than an update. Unlike protocol (v1.49.0) and server-sdk-go/v2 (v2.17.0), which move forward, sipgo moves backward. Since sipgo is used throughout pkg/sip/* (e.g. pkg/sip/server.go, pkg/sip/client.go, pkg/sip/inbound.go, pkg/sip/outbound.go), any API added after the older commit would break compilation, and any bug fixed between the two commits would be reintroduced.
Prompt for agents
The sipgo dependency in go.mod line 17 is pinned to v0.13.2-0.20250410120437-ca5b8ca7b53d, whose pseudo-version timestamp (2025-04-10) is earlier than the previously pinned v0.13.2-0.20260519205735-a5b4a38b6ceb (2026-05-19). Go orders same-base pseudo-versions by timestamp, so this is effectively a ~13 month downgrade of github.com/livekit/sipgo, not an update, despite the PR title. Verify that commit ca5b8ca7b53d is genuinely the intended newer revision (the livekit/sipgo history may have been rewritten/rebased, causing an earlier commit date). If this downgrade is unintended, re-pin sipgo to the latest intended commit and regenerate go.sum. If it is intended, confirm that all sipgo APIs used across pkg/sip/* still exist at ca5b8ca7b53d and that no needed fixes are lost.
Was this helpful? React with 👍 or 👎 to provide feedback.
This PR contains the following updates:
v1.48.1-0.20260624204523-bd5703442db6→v1.49.0v1.50.1(+1)v2.16.7-0.20260625120102-b6d1838861e7→v2.17.0v2.18.1(+1)a5b4a38→ca5b8caRelease Notes
livekit/protocol (github.com/livekit/protocol)
v1.49.0Compare Source
v1.48.2Compare Source
livekit/server-sdk-go (github.com/livekit/server-sdk-go/v2)
v2.17.0Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.